Methods systems, and apparatuses for implementing upstream power control for DSL

ABSTRACT

In accordance with embodiments disclosed herein, there are provided apparatuses, systems and methods for implementing upstream power control for DSL communications. For example, such a system may include means for: dividing a plurality of DSL lines into a first group of DSL lines and a second group of DSL lines based on characteristics common to each of the DSL lines within the respective first and second groups; determining attainable upstream data rates for the first and second groups of DSL lines according to the characteristics of each group; selecting upstream power control parameters to apply to each of the first and second groups of DSL lines based on the attainable upstream data rates determined; and instructing the DSL lines of the first and second groups to adopt the selected upstream power control parameters. Other related embodiments are disclosed.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of previously filed and copendingU.S. patent application Ser. No. 14/786,438, entitled “METHODS, SYSTEMS,AND APPARATUSES FOR IMPLEMENTING UPSTREAM POWER CONTROL FOR DSL,” namingas inventors Georgios Ginis, Ming-Yang Chen, and Mehdi Mohseni, andfiled Jul. 29, 2016, which is the US national stage application under 35USC § 371 of PCT Patent Application No. PCT/US13/37805, filed Apr. 23,2013, which applications are hereby incorporated herein by reference intheir entireties.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

The subject matter described herein relates generally to the field ofcomputing, and more particularly, to methods, systems, and apparatusesfor implementing upstream power control for DSL.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also correspond toembodiments of the claimed subject matter.

In the communications arts there is a phenomenon known as the “near-farproblem” in which receivers capturing strong signals have difficultysimultaneously detecting weaker signals. In the DSL arts specifically,an upstream near-far problem may exist in which crosstalk from near-end(strong) users impacts signaling of far-end (weak) users, or in whichusers coupled with short loops exhibit stronger signals than users onlonger more attenuated loops, and thus, the stronger signaling userssignificantly degrade the weaker signaling users' data rates.

DSL transmissions are negatively impacted by crosstalk and such effectsare exhibited most strongly with short loops. Moreover, such crosstalkis especially problematic for transmissions in the upstream directionwhere DSL upstream transmissions on short loops cause very strongcrosstalk to DSL upstream transmissions on longer loops, thus resultingin the well known near-far problem.

In a laboratory setting it may be feasible to architect an experimentwith DSL lines or loops of approximately equal length such that acrossthe board power control parameters would suffice. Optionally, vectoringcould be applied to all of the lines so as to perfectly cancel allcrosstalk. However, it is very well understood by those skilled in therelevant arts that such pristine laboratory conditions simply do nottranslate to the real world. Actual DSL deployments in the fieldcommonly consist of both shorter and longer DSL loops as well aspotentially non-vectored lines co-located with DSL loops of a vectoredgroup.

Instituting what is known as a power back-off for all lines is a simplesolution to reduce crosstalk but also results in lower transmissionrates and is therefore impractical for many deployments. Vectoring asnoted above greatly reduces crosstalk but requires new equipment to bedeployed and thus may not be available or may only be available on asub-set of co-located DSL lines, and thus does not solve the problem ofcrosstalk for those non-vectored lines or for vectored lines whichoperate near non-vectored lines.

The present state of the art may therefore benefit from methods,systems, and apparatuses for implementing upstream power control for DSLas described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example, and not by way oflimitation, and will be more fully understood with reference to thefollowing detailed description when considered in connection with thefigures in which:

FIG. 1 illustrates an exemplary architecture in which embodiments mayoperate;

FIG. 2A illustrates an exemplary architecture within which embodimentsmay operate;

FIG. 2B illustrates another exemplary architecture within whichembodiments may operate;

FIG. 2C illustrates another exemplary architecture within whichembodiments may operate;

FIG. 2D illustrates another exemplary architecture within whichembodiments may operate;

FIG. 2E illustrates another exemplary architecture within whichembodiments may operate;

FIG. 2F illustrates another exemplary architecture within whichembodiments may operate;

FIGS. 3 and 4 depict flow diagrams illustrating methods for implementingand using improved upstream power control schemes for DSL communicationsin accordance with described embodiments;

FIG. 5 illustrates a diagrammatic representation of a system inaccordance with which embodiments may operate, be installed, integrated,or configured; and

FIG. 6 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system.

DETAILED DESCRIPTION

Described herein are apparatuses, systems and methods for implementingupstream power control for DSL communications.

In accordance with one embodiment, an exemplary system may include meansfor: dividing a plurality of DSL lines into a first group of DSL linesand a second group of DSL lines based on characteristics common to eachof the DSL lines within the respective first and second groups;determining attainable upstream data rates for the first and secondgroups of DSL lines according to the characteristics of each group;selecting upstream power control parameters to apply to each of thefirst and second groups of DSL lines based on the attainable upstreamdata rates determined; and instructing the DSL lines of the first andsecond groups to adopt the selected upstream power control parameters.

Power control may be applied to short DSL loops or lines to prevent verylow rates or non-connection events on longer loops which are negativelyimpacted by the near-far problem described above. In a fully vectoredsystem crosstalk is completely canceled and there is no need for shortDSL lines to back off power on behalf of the long lines because thenear-far problem does not exist. However, many deployments are not fullyvectored, and as such, the near-far problem remains where some but notall DSL loops are vectored or where none of the DSL loops are vectored.The near-far problem may also occur between two groups of linesbelonging to different vectored groups in which lines within therespective vectored groups do not exhibit crosstalk onto one another butalien crosstalk may occur between the vectored groups, despite all linesbeing vectored. Other types of groupings may also benefit fromtechniques to enhance performance of one group over another or improveoverall operation of the DSL communication system by grouping linesaccording to common characteristics and then determining and applyingdifferent upstream power control parameters to each of the respectivegroups.

Take for instance a grouping of 24 DSL lines. Half of the customers signup for 10 Mbps service and the other half of the customers pay extrasubscription fees to sign up for 20 Mbps. The lines in each of the twogroups are likely to have different line lengths as customers do notselect their tier of service based on how far their CPE side modem isfrom a DSLAM of a DSL service provider. Most customers are likelyunaware that such constraints even exist. Nevertheless, a DSL serviceprovider will benefit from the flexibility of offering customers highersubscription tiers, even at longer loop lengths from a DSLAM as thegreater portion of customers that can be offered such service willpresumably yield greater service revenues to the DSL service providerand greater choice, flexibility, and satisfaction for the consumers.

Given the groupings then of the higher tier subscribers and the lowertier subscribers, a maximum length may be determined for the lines ofthe higher subscription tier group and then through modeling or DSLestimation a management device may determine the maximum upstream datarate that can be offered to the higher tier of subscribers or amanagement device may alternatively or additionally determine a maximumlength of DSL line capable of being serviced at the higher subscriptiontier based upon the requisite data rates for that tier.

Appropriate upstream power parameters are then determined for the groupssuch that the consumers in the higher subscription tier will achievetheir promised data rates while also permitting acceptable data ratesfor the lower tier subscribers. Such techniques are described in furtherdetail below including additional and alternative considerationsutilized to determine the attainable data rates and necessary upstreampower parameters to attain such rates.

In the following description, numerous specific details are set forthsuch as examples of specific systems, languages, components, etc., inorder to provide a thorough understanding of the various embodiments. Itwill be apparent, however, to one skilled in the art that these specificdetails need not be employed to practice the disclosed embodiments. Inother instances, well known materials or methods have not been describedin detail in order to avoid unnecessarily obscuring the disclosedembodiments.

In addition to various hardware components depicted in the figures anddescribed herein, embodiments further include various operations whichare described below. The operations described in accordance with suchembodiments may be performed by hardware components or may be embodiedin machine-executable instructions, which may be used to cause ageneral-purpose or special-purpose processor programmed with theinstructions to perform the operations. Alternatively, the operationsmay be performed by a combination of hardware and software, includingsoftware instructions that perform the operations described herein viamemory and one or more processors of a computing platform.

Embodiments also relate to a system or apparatus for performing theoperations herein. The disclosed system or apparatus may be speciallyconstructed for the required purposes, or it may comprise a generalpurpose computer selectively activated or reconfigured by a computerprogram stored in the computer. Such a computer program may be stored ina non-transitory computer readable storage medium, such as, but notlimited to, any type of disk including floppy disks, optical disks,flash, NAND, solid state drives (SSDs), CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring non-transitory electronic instructions, each coupled to acomputer system bus. In one embodiment, a non-transitory computerreadable storage medium having instructions stored thereon, causes oneor more processors within an apparatus to perform the methods andoperations which are described herein. In another embodiment, theinstructions to perform such methods and operations are stored upon anon-transitory computer readable medium for later execution.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus nor are embodimentsdescribed with reference to any particular programming language. It willbe appreciated that a variety of programming languages may be used toimplement the teachings of the embodiments as described herein.

FIG. 1 illustrates an exemplary architecture 100 in which embodimentsmay operate. Asymmetric Digital Subscriber Line (ADSL) systems (one formof Digital Subscriber Line (DSL) systems), which may or may not includesplitters, operate in compliance with the various applicable standardssuch as ADSL1 (G.992.1), ADSL-Lite (G.992.2), ADSL2 (G.992.3),ADSL2-Lite G.992.4, ADSL2+(G.992.5) and the G.993.x emergingVery-high-speed Digital Subscriber Line or Very high-bitrate DigitalSubscriber Line (VDSL) standards, as well as the G.991.1 and G.991.2Single-Pair High-speed Digital Subscriber Line (SHDSL) standards, allwith and without bonding, and/or the G.997.1 standard (also known asG.ploam).

The G.997.1 standard specifies the physical layer management for ADSLtransmission systems based on the clear, Embedded Operation Channel(EOC) defined in G.997.1 and use of indicator bits and EOC messagesdefined in the G.992.x, G.993.x and G.998.4 standards. Moreover, G.997.1specifies network management elements content for configuration andperformance management. In performing the disclosed functions, systemsmay utilize a variety of operational data (which includes performancedata) that is available at an Access Node (AN).

In FIG. 1, users terminal equipment (TE) 102 (e.g., a Customer PremisesEquipment (CPE) device or a remote terminal device, network node, LANdevice, etc.) is coupled to a home network 104, which in turn is coupledto a Network Termination (NT) Unit 108. Multiple xTU devices (“allTransceiver Unit” devices) are further depicted. An xTU providesmodulation for a DSL loop or line (e.g., DSL, ADSL, VDSL, etc.). In oneembodiment, NT unit 108 includes an xTU-R (xTU Remote) 122 (for example,a transceiver defined by one of the ADSL or VDSL standards), or anyother suitable network termination modem, transceiver or othercommunication unit. NT unit 108 also includes a Management Entity (ME)124. Management Entity 124 may be any suitable hardware device, such asa microprocessor, microcontroller, or circuit state machine in firmwareor hardware, capable of performing as required by any applicablestandards and/or other criteria. Management Entity 124 collects andstores, among other things, operational data in its ManagementInformation Base (MIB), which is a database of information maintained byeach ME capable of being accessed via network management protocols suchas Simple Network Management Protocol (SNMP), an administration protocolused to gather information from a network device to provide to anadministrator console/program; via Transaction Language 1 (TL1)commands, TL1 being a long-established command language used to programresponses and commands between telecommunication network elements; orvia a TR-69 based protocol. “TR-69” or “Technical Report 069” is inreference to a DSL Forum technical specification entitled CPE WANManagement Protocol (CWMP) which defines an application layer protocolfor remote management of end-user devices. XML or “eXtended MarkupLanguage” compliant programming and interface tools may also be used.

Each xTU-R 122 in a system may be coupled with an xTU-C (xTU Central) ina Central Office (CO) or other central location. The xTU-C 142 islocated at an Access Node (AN) 114 in Central Office (CO) 146. AManagement Entity 144 likewise maintains an MIB of operational datapertaining to xTU-C 142. The Access Node 114 may be coupled to abroadband network 106 or other network, as will be appreciated by thoseskilled in the art. Each of xTU-R 122 and xTU-C 142 are coupled togetherby a U-interface/loop 112, which in the case of ADSL may be a twistedpair line, such as a telephone line, which may carry other communicationservices besides DSL based communications. Either Management Entity 124or Management Entity 144 may implement and incorporate a managementdevice 170 as described herein. The management device 170 may beoperated by a service provider or may be operated by a third party,separate from the entity which provides DSL services to end-users. Thus,in accordance with one embodiment, the management device 170 is operatedand managed by an entity which is separate and distinct from atelecommunications operator responsible for a plurality of digitalcommunication lines such as copper twisted pair telephone lines overwhich such telecommunication services are delivered tosubscribers/customers. For instance, the management device may operatewithin the so called cloud as a cloud service provided by a third partydistinct from the communications system operator or the service providerfor the communications system.

Several of the interfaces shown in FIG. 1 are used for determining andcollecting operational data. The Q interface 126 provides the interfacebetween the Network Management System (NMS) 116 of the operator andManagement Entity 144 in Access Node 114. Parameters specified in theG.997.1 standard apply at the Q interface 126. The near-end parameterssupported in Management Entity 144 may be derived from xTU-C 142, whilefar-end parameters from xTU-R 122 may be derived by either of twointerfaces over the U-interface. Indicator bits and EOC messages may besent using embedded channel 132 and provided at the Physical MediumDependent (PMD) layer, and may be used to generate the required xTU-R122 parameters in Management Entity 144. Alternately, the Operations,Administration and Maintenance (OAM) channel and a suitable protocol maybe used to retrieve the parameters from xTU-R 122 when requested byManagement Entity 144. Similarly, the far-end parameters from xTU-C 142may be derived by either of two interfaces over the U-interface.Indicator bits and EOC message provided at the PMD layer may be used togenerate the required xTU-C 142 parameters in Management Entity 124 ofNT unit 108. Alternately, the OAM channel and a suitable protocol may beused to retrieve the parameters from xTU-C 142 when requested byManagement Entity 124.

At the U-interface (also referred to as loop 112), there are twomanagement interfaces, one at xTU-C 142 (the U-C interface 157) and oneat xTU-R 122 (the U-R interface 158). The U-C interface 157 providesxTU-C near-end parameters for xTU-R 122 to retrieve over theU-interface/loop 112. Similarly, the U-R interface 158 provides xTU-Rnear-end parameters for xTU-C 142 to retrieve over the U-interface/loop112. Interfaces V 156 and V-C 159 are further depicted within the CO 146at different points of the loop 112. The parameters that apply may bedependent upon the transceiver standard being used (for example, G.992.1or G.992.2). The G.997.1 standard specifies an optional Operation,Administration, and Maintenance (OAM) communication channel across theU-interface. If this channel is implemented, xTU-C and xTU-R pairs mayuse it for transporting physical layer OAM messages. Thus, the xTUtransceivers 122 and 142 of such a system share various operational datamaintained in their respective MIBs.

Management device 170 is depicted as operating at various optionallocations and being capable of implementing improved techniques forupstream power control as described herein in accordance with severalalternative embodiments. Management device 170 may be interfaced to aDSL communications system via broadband network 106, as is the case withembodiments where the management device 170 operates as a cloud basedservice via a third party provider distinct from the DSL operatorresponsible for the DSL communication components or the DSL servicesprovider which sells internet services to end-user subscribers.Management device 170 may be interfaced via the Network ManagementSystem (NMS) 116 and in yet another embodiment, management device 170 isconnected with a NT unit 108 or with xTU-R 122 over the G-interface 159.In an alternative embodiment, the management device 170 operates at aCPE side, such as communicatively interfaced between a home network 104(e.g. a LAN) and TE 102 and may optionally operate within TE 102 (e.g.,within a CPE modem).

As used herein, the terms “user,” “subscriber,” and/or “customer” referto a person, business and/or organization to which communicationservices and/or equipment are and/or may potentially be provided by anyof a variety of service provider(s). Further, the term “customerpremises” refers to the location to which communication services arebeing provided by a service provider. For an example Public SwitchedTelephone Network (PSTN) used to provide DSL services, customer premisesare located at, near and/or are associated with the network termination(NT) side of the telephone lines. Example customer premises include aresidence or an office building.

As used herein, the terms “user,” “subscriber,” and/or “customer” referto a person, business and/or organization to which communicationservices and/or equipment are and/or may potentially be provided by anyof a variety of service provider(s). Further, the term “customerpremises” refers to the location to which communication services arebeing provided by a service provider. For an example Public SwitchedTelephone Network (PSTN) used to provide DSL services, customer premisesare located at, near and/or are associated with the network termination(NT) side of the telephone lines. Example customer premises include aresidence or an office building.

As used herein, the term “service provider” refers to any of a varietyof entities that provide, sell, provision, troubleshoot and/or maintaincommunication services and/or communication equipment. Example serviceproviders include a telephone operating company, a cable operatingcompany, a wireless operating company, an internet service provider, orany service that may independently or in conjunction with a broadbandcommunications service provider offer services that diagnose or improvebroadband communications services (DSL, DSL services, cable, etc.).

Additionally, as used herein, the term “DSL” refers to any of a varietyand/or variant of DSL technology such as, for example, Asymmetric DSL(ADSL), High-speed DSL (HDSL), Symmetric DSL (SDSL), and/or Veryhigh-speed/Very high-bit-rate DSL (VDSL). Such DSL technologies arecommonly implemented in accordance with an applicable standard such as,for example, the International Telecommunications Union (I.T.U.)standard G.992.1 (a.k.a. G.dmt) for ADSL modems, the I.T.U. standardG.992.3 (a.k.a. G.dmt.bis, or G.adsl2) for ADSL2 modems, I.T.U. standardG.992.5 (a.k.a. G.ads12plus) for ADSL2+ modems, I.T.U. standard G.993.1(a.k.a. G.vdsl) for VDSL modems, I.T.U. standard G.993.2 for VDSL2modems, I.T.U. standard G.993.5 for DSL modems supporting Vectoring,I.T.U. standard G.998.4 for DSL modems supporting retransmissionfunctionality, I.T.U. standard G.994.1 (G.hs) for modems implementinghandshake, and/or the I.T.U. G.997.1 (a.k.a. G.ploam) standard formanagement of DSL modems.

References to connecting a DSL modem and/or a DSL communication serviceto a customer are made with respect to exemplary Digital Subscriber Line(DSL) equipment, DSL services, DSL systems and/or the use of ordinarytwisted-pair copper telephone lines for distribution of DSL services, itshould be understood that the disclosed methods and apparatus tocharacterize and/or test a transmission medium for communication systemsdisclosed herein may be applied to many other types and/or variety ofcommunication equipment, services, technologies and/or systems. Forexample, other types of systems include wireless distribution systems,wired or cable distribution systems, coaxial cable distribution systems,Ultra High Frequency (UHF)/Very High Frequency (VHF) radio frequencysystems, satellite or other extra-terrestrial systems, cellulardistribution systems, broadband power-line systems and/or fiber opticnetworks. Additionally, combinations of these devices, systems and/ornetworks may also be used. For example, a combination of twisted-pairand coaxial cable interfaced via a balun connector, or any otherphysical-channel-continuing combination such as an analog fiber tocopper connection with linear optical-to-electrical connection at anOptical Network Unit (ONU) may be used.

The phrases “coupled to,” “coupled with,” connected to,” “connectedwith” and the like are used herein to describe a connection between twoelements and/or components and are intended to mean coupled/connectedeither directly together, or indirectly, for example via one or moreintervening elements or via a wired/wireless connection. References to a“communication system” are intended, where applicable, to includereference to any other type of data transmission system.

In the FIGS. 2A through 2G that follow there are described a variety ofdifferent groupings and configurations which may be accommodated throughthe described means for implementing upstream power controls for DSLsystem communications.

FIG. 2A illustrates an exemplary architecture 200 in which embodimentsmay operate. In particular, DSLAM 275 is shown connected with managementdevice 170 via interface 230 or optionally connected with managementdevice 170 via interface 230 through network 290 where the managementdevice 170 operates remotely and is connected, for example, via thepublic internet or the cloud. Subscriber premises 250 are connected withthe DSLAM 275 in which a first subset is connected via long loops 231and a second sub-set is connected via short loops 232. The long loops231 and short loops 232 traverse a common cable 235 and are affected bycrosstalk 240. Element 226 showing an increasing distance from a DSLAMdepicts that some of the subscriber premises are farther away from theDSLAM 275 and thus have longer loops than other subscriber premises 250.

Crosstalk 240 coupling is especially serious for upstream transmissionsin which there is a mixture of long and short loops as depicted here dueto the DSL upstream transmissions on short loops causing very strongcrosstalk 240 coupling to DSL upstream transmissions on the long loopsresulting in the near-far problem.

The problem for a DSL service provider or DSL operator is that higherdata rates are required to service customers having subscribed tohigher-tier (e.g., more expensive) service products, and as such, theservice provider must configure the lines so that the higher tiercustomers receive the level of service they have paid for while at thesame time ensuring that lower tier subscribers continue to receiveadequate data rates despite such rates being lower than the higher tiercustomers. Problematically, without upstream power control means, theshort loops 232 will exhibit such strong crosstalk 240 coupling to thelong loops 231 that it may not be possible to provide the subscriberpremises 250 with a higher level tier of service, especially wherehigher tier subscribers are connected with longer DSL loops 231 thansubscribers of a lower tier service product.

Despite having a mixture of both long and short DSL loops, themanagement device 170 described herein is capable of implementingupstream power control so as to improve communications on both the longand the short loops to the extent that higher tier services includingfaster data rates may be offered to subscriber premises 250 regardlessof whether they are communicatively interfaced to the DSLAM 275 via thelong loops 231 or the short loops 232.

FIG. 2B illustrates another exemplary architecture 201 in whichembodiments may operate. The DSLAM 275, common cable 235, crosstalk,network 290, interface 230, and the management device remain. However,subscriber premises 250 have now been grouped into group A at element234 with a long and a short loop and group B at element 233 also havinga long and a short loop.

In such an embodiment, two or more groups of lines are served from aDSLAM 275 node, each of the groups having different lengths for theirrespective loops and each of the groups having different characteristicsfor their DSL lines/loops. The grouping may occur based on a variety ofcharacteristics other than line length. Different characteristics caninclude: different frequency band-plan (e.g., the frequency usage),different DSL technology, equipment, standard profiles, protocols,different DSLAM line-cards, service tiers, and so forth. For instance,in one embodiment grouping occurs without regard to loop length possiblybut not necessarily resulting in each group having both long and shortloops (e.g., grouped according to service tiers, etc.).

FIG. 2C illustrates another exemplary architecture 202 in whichembodiments may operate. In this embodiment there are depicted DSL lineswhich are grouped based at least in part on their loop lengths such thata first group has loops within a selected range of lengths and anothergroup has loops within a different selected range of lengths. Forinstance long loops may be grouped together forming the group of longloops at element 237A and short loops may be grouped together formingthe group of short loops at element 237B. Also, two groups are depictedhere for the sake of simplicity but there may be more than two groupsinto which a plurality of DSL lines are sub-divided regardless of thecharacteristics which are used to form the groupings upon which todivide the plurality of lines.

FIG. 2D illustrates another exemplary architecture 203 in whichembodiments may operate. In particular, there is depicted a group ofvectored lines at element 239 coupled with the vectored DSLAM 276 andalso a group of non-vectored lines at element 238. As can be seen fromthe figure, both the non-vectored group of lines and the vectored groupof lines share the same common cable 235 resulting in the two distinctgroups having crosstalk 240 between them. This crosstalk may beconsidered alien crosstalk 240, and as depicted, may originate from thegroup of non-vectored lines 238 and electromagnetically couple onto thegroup of vectored lines 239, negatively affecting the group of vectoredlines 239 due to the crosstalk 240 being un-cancelled by the vectoringapplied to the group of vectored lines. Although same-binder crosstalkis strongest, crosstalk between binders is significant in many cases andso vectoring often spans multiple binders within a single cable 235.

Grouping characteristics may thus include vectoring status, forinstance, in which a first group contains vectored lines and a secondgroup contains non-vectored lines. Other characteristics upon whichgroupings may be based include service products for the groups (e.g.,higher tier vs. lower tier) or lines using a different band-plan andthus may be susceptible to differing ranges of crosstalk or requiredifferent power parameters to operate at the respective frequency bandsutilized by each group, or based upon different capabilities of DSLequipment coupled with the DSL loops, such as vectoring capableequipment and non-vectoring capable equipment, or such as equipmentusing VDSL profile 8 a and equipment using VDSL profile 8 b.

If no upstream power control were applied to the loops of either groupthen the long lines may suffer from very low upstream rates because ofstrong crosstalk from the short loops which then leads to a very“unfair” rate distribution. Moreover, even if power controls are appliedto the lines but there is no differentiation made between the differentgroups of lines then customers in a first group with an expensiveservice product may get the same or inferior rates relative to thecustomers in a second group with the less expensive product.

Failing to differentiate between groups of lines may also undermine thebenefits of vectoring. For instance, data rates of vectored lines in afirst group may remain poor, notwithstanding the vectoring capabilities,due to crosstalk from short non-vectored loops in a second group, thuswasting the expense of provisioning the more advanced vectoring capableequipment (e.g., DSLAMs, line cards, CPE modems, etc.).

Conventional upstream power management techniques have applied the same“upstream power back-off” strategy across all twisted pair DSLlines/loops by utilizing the same parameters across an entire populationof DSL lines without differentiation. Such a technique does improve therates of long loops, and provides a more “fair” distribution of ratesamong long and short loops overall. However, the common “upstream powerback-off” strategy is less than ideal because there remains nodifferentiation between two groups of lines, and as such, the problemsdescribed above remain. For instance, it may be necessary to providehigher rates to higher tier and higher paying subscribers regardless ofwhether they happen to be connected to the DSLAM 275 via a longer orshorter loop and such differentiation cannot be accomplished utilizing aconventional technique which applies the same upstream power back-off toall lines.

Another solution, therefore, is to determine and then apply an “optimumspectrum balancing” for every one of a plurality of DSL lines. Such anapproach is not utilized in the conventional arts outside of simulationor laboratory conditions because it is extremely complex to determinethe optimal upstream rate and power distribution for each line which inturn translates to very high computational demands which may not befeasible to fulfill for large-scale deployments of DSL service providernetworks. The complexity results from the wide array of differingsolutions that require modeling based upon the exact loop topology for aparticular deployment and the necessity to solve for complexmathematical relationships among the many loops and their respectivecharacteristics. Computational requirements for network managementhardware, management bandwidth and DSL equipment data, and controlinterfaces to solve for this level of complexity would be costprohibitive to a DSL system operator.

Further depicted are the vector capable CPEs 251 and non-vectored DSLcommunications to the non-vector capable CPEs at element 252. In thisembodiment, the vectored DSLAM 276 is connected to all lines (238 and239) in the area. One set of lines are connected to vector-capable CPEsresulting in the group of vectored lines 239 and the remaining lines areconnected to non-vector-capable CPEs resulting in the group ofnon-vectored lines 238. Here the characteristic utilized to divide theplurality of lines into groups is therefore vectoring capability of therespective CPE at the subscriber premises 250. The group of non-vectoredlines 238 results in strong crosstalk 240 coupling onto thetransmissions of the group of vectored lines 239 and this crosstalk isnot canceled as it is received as alien crosstalk from a source outsideof the group of vectored lines 239. The group of vectored lines 239 alsoexhibits crosstalk coupling onto transmissions of the group ofnon-vectored lines 238. Such crosstalk coupling reduces downstream andupstream transmission rates of the group of vectored lines 239 relativeto the case where there are no lines outside of the group of vectoredlines 239.

Thus, the management device 170 applies upstream power controltechniques using different upstream power control parameters for thedifferent groups of lines.

FIG. 2E illustrates another exemplary architecture 204 in whichembodiments may operate. In particular, there are both a vectored DSLAM210 and a non-vectored DSLAM 220 or alternatively non-vectored linecards (e.g., where DSLAMs 210 and 220 are embodied by separate linecards within a single DSLAM). The vectored DSLAM 210 services the vectorcapable CPEs 251 via the group of vectored lines 239 and thenon-vectored DSLAM services the non-vector capable CPEs 252 via thegroup of non-vectored lines 238.

As before, the group of non-vectored lines 238 create strong crosstalkfor the transmissions on the group of vectored lines 239, and viceversa. The crosstalk reduces the downstream and upstream transmissionrates of the vectored lines relative to the case where no non-vectoredlines existed, or where the non-vectored lines were actually vectored.

Service providers must plan for services that can be offered tocustomers and part of such planning is the ability to know whattransmission rates can feasibly be offered and provided to a customer.Having non-vectored lines neighboring vectored lines makes it difficultto predict the transmission rates of the vectored lines and yet at thesame time, it may be impractical for the service provider to separatevectored pairs of lines from non-vectored pairs, for instance, due tosuch lines being common to the same binder or a common cable 235. Aswith the preceding examples, it is further impractical to change thedistance from which a DSL services subscriber is located from a DSLAMand it may be impractical to control which DSL subscribers in ageographic area have vectoring capable CPEs versus non-vectoring capableCPEs. For example, some customers may not wish to upgrade their CPEmodem and it would be wasteful for the DSL service provider to provisionvectoring capable CPE modems to those customers who choose not toupgrade and thus retain a lower tier service plan which is presumablyprovided at a lower subscription rate.

FIG. 2E illustrates another exemplary architecture 205 in whichembodiments may operate. In particular, DSL lines 211 are depicted inadditional detail, broken down into two distinct groups in thisparticular example. Specifically, there is a first subset of the DSLlines 211 that are vectored lines and thus constitute a first group 212and there is a second subset of the DSL lines 211 that are not in thevectored group and thus constitute a second group 213. A plurality oflines may also be divided according to other characteristics such astier plan, line length, frequency band plan, etc.

Management device 170 is depicted as being communicatively interfacedwith the plurality of DSL lines 211 through the interface to the DSLlines at element 214. For instance, the interface may traverse throughtransceivers, CPE modems, DSLAMs, or other equipment so as to provide acommunications interface between the DSL lines and the management device170 such that the management device 170 is capable to collectoperational data 216 from the DSL lines 211 and additionally issue orsend optimization instructions 218 including, for example, configurationchanges, to the DSL lines 211 as depicted by the information flowelements between the DSL lines 211 and the management device 170. Suchoptimization instructions 218 may specify different upstream powercontrol parameters for each of the two groups or different instructionsfor more than two groups where the management device divides a pluralityof lines into more than a first and a second group.

FIGS. 3 and 4 depict flow diagrams illustrating methods 300 and 400 forimplementing and using improved upstream power control schemes for DSLcommunications in accordance with described embodiments. Methods 300 and400 may be performed by processing logic that may include hardware(e.g., circuitry, dedicated logic, programmable logic, microcode, etc.),software (e.g., instructions run on a processing device to performvarious operations such as interfacing, managing, receiving,controlling, analyzing, collecting, generating, monitoring, diagnosing,or some combination thereof). In one embodiment, one or both of methods300 and 400 are performed or coordinated via an apparatus such as thatdepicted at element 170 of FIG. 1. Some of the blocks and/or operationslisted below are optional in accordance with certain embodiments. Thenumbering of the blocks presented is for the sake of clarity and is notintended to prescribe an order of operations in which the various blocksmust occur.

FIG. 3 depicts a process flow for method 300 beginning with block 305having processing logic for specifying a maximum loop length of group Aand maximum loop length of group B. Alternatively, processing mayspecify a range of acceptable loop lengths into which a plurality ofloops are divided so as to form the group A and group B sub-sets. Othergrouping considerations are also permissible as is described above.

At block 310, processing logic specifies an expected number of lines ingroup A (N1) and expected number of lines in group B (N2). According toone embodiment, channel, crosstalk, and noise models are selected so asto enable DSL modeling and estimation so that the lines may becharacterized and modeled sufficient to enable upstream rates to bespecified and the corresponding upstream power control parametersidentified to achieve the specified rates. Known standardized models maybe utilized or specialized models may be constructed based on lab orfield observations. The expected number of lines for the respectivegroups may then be provided to the chosen models input as parameters.

At block 315, processing logic specifies an upstream rate of the linesin group B. For instance, the upstream rate for the lines in the groupmay be mandated by equipment capabilities, mandated by a DSL systemoperator and thus outside of the control of the management device 170,the upstream rate may be specified so as to fulfill a requiredsubscriber tier level (e.g., 15 mbps, 50 mbps, etc.), or selected basedon other considerations available to a management device implementingthe upstream power control scheme.

At block 320, processing logic identifies upstream power controlparameters for the lines in group B. For instance, using the modelingconducted based on the channel and crosstalk and noise models selected;processing logic may identify upstream power control parameters tofulfill the specified data rate. In one embodiment upstream powercontrol parameters of lines in group B are identified by assuming N1+N2pairs of group B at a maximum loop length for group B to determine theupstream power control parameters necessary to achieve the specifiedupstream rate for the lines in group B. Processing may further identifya maximum upstream rate for the lines of group A which is feasible basedon the modeling given the data rate specified for group B.

At block 325, processing logic identifies upstream power controlparameters for the lines in group A. For instance, the upstream powerparameters for group A may be further identified so as to attain themaximum upstream rate determined for group A. In such a way, the datarate of group A may be maximized but subjected first to the specifieddata rate of group B. Such a technique may be helpful where group Aconstitutes lines operating at a higher price-tier than the lines ofgroup B and must therefore conform to the specified data rates, where asthe remaining lines of group B should simply be maximized for the sakeof ensuring optimal customer satisfaction but do not necessarily requireany particular data rate or require a rate which is lower than that ofgroup A. In such a way, processing is able to maximize the data rate forthe group having preference (e.g., due to a higher priced service tier,etc.) while keeping a promised level of service for the non-preferredgroup (e.g., other lines associated with a lower priced service tier,etc.). Such performance trade-offs to the benefit of the preferred groupmay be obtained by varying the promised level of service fornon-preferred group.

As with the data rate for group B, the data rate and correspondingupstream power control parameters may also be based upon the modeling orbased on other estimation techniques familiar to the DSL arts.

Such a technique is further advantageous as a set of upstream powerback-off (UPBO) parameters may be determined separately for each foreach of the distinct groups, for instance, groups A and B from thepreceding example. In such a way, different UPBO settings may be appliedto distinct groups having disparate characteristics, something which isnot feasible with conventionally available techniques. Having differentUPBO settings is also less computationally intensive to calculate thandetermining UPBO settings for every line individually and is lesscomplex to implement onto the operating DSL lines than individualsettings for every line, assuming such solutions could be determined.Other upstream power control parameters may be used in place of UPBOsettings or in addition to UPBO settings.

In one embodiment, certain assumptions may be made as to the lines ofthe different groups. For example, computational complexity may bereduced by assuming a worst-case length for each group, for instance, byassigning an assumed length equal to or approximating a DSL line in agroup having the longest length, and then utilizing this assumed lengthfor all DSL lines in the same group. By assuming equal lengths for DSLsin a group, the optimization problem is greatly simplified, because theoptimization space is reduced, and a solution is only needed for eachgroup, instead of a solution for each line. Although an assumed lengthis utilized which may not concur with actual lengths for some of the DSLlines in a group, testing of such a technique has shown that data rateperformance is very close to that which is achieved by an optimalspectrum balancing technique in which individual upstream power controlparameters are determined for every single line individually. Thus,computational efficiency is realized while still benefitting from theimproved data rate performance of more complex optimization techniqueswhich may be infeasible for DSL components provisioned to the field.Other characteristics may also be assumed in addition to or in place ofassuming line length.

It was discovered through testing and experimentation that thecomplexity of solving for many DSL lines of differing line lengths canbe greatly reduced through the described grouping and making certainassumptions about the lines despite these assumptions not necessarilybeing true for all lines in a particular group. For instance,determining an optimal solution for all lines in a population havingdifferent line lengths is so computationally complex that it can only besolved in a laboratory environment and not for large-scale DSLdeployments in the field. However, assuming that all lines in a firstgroup have a first assumed maximum length and assuming all lines in asecond group have a second assumed maximum length reduces the complexityof the solution to the point that typical field deployment componentspossess sufficient computational resources. Despite these assumptions,it was discovered that a solution can be attained for two groups whichis virtually 100% as good as the optimal solution computed based onactual loop lengths for every one of the population of DSL lines. Formore than two groups a solution of approximately 92% to 95% as good asthe optimal solution is attainable through the described techniques.

Utilizing assumed values was a non-intuitive approach to solving theproblem because providing inaccurate input for some of the DSL lines toa model or DSL estimation means would presumably render garbage orinaccurate results due to the mathematical relationships between thevarious lines based on their inputs to the modeling or estimation meansbeing corrupted or falsified. Yet, through the grouping schemesdescribed, near optimal solutions can nevertheless be attained with farless complexity providing an unexpected benefit and result of thedescribed approach.

At block 330, processing logic applies the upstream rates and powercontrol parameters to the respective lines of both groups A and B. Forexample, optimization instructions may be sent to DSL equipment such asCPE modems, DSLAMs, line cards, etc., instructing the equipment to adoptthe upstream rates and power control parameters established above.

FIG. 4 presents an alternative processes flow for method 400 whichbegins with block 405 having processing logic for dividing a pluralityof DSL lines into a first group of DSL lines and a second group of DSLlines based on characteristics common to each of the DSL lines withinthe respective first and second groups.

At block 410, processing logic determines attainable upstream data ratesfor the first and second groups of DSL lines.

At block 415, processing logic selects upstream power control parametersto apply to each of the first and second groups of DSL lines based onthe attainable upstream data rates determined.

At block 420, processing logic instructs the DSL lines of the first andsecond groups to adopt the selected upstream power control parameters.

A variety of alternative method flows may also be utilized in accordancewith the described embodiments. For example, in one alternative methodflow, operations include dividing a plurality of DSL lines into a firstgroup of DSL lines and a second group of DSL lines based oncharacteristics common to each of the DSL lines within the respectivefirst and second groups; modeling the first and second groups of DSLlines to determine data rates attainable for each of the first andsecond groups and corresponding upstream power parameters required toattain the data rates on the first and second groups respectively;selecting a first data rate to apply to the first group of DSL linesbased on the data rates attainable as determined by the modeling; andselecting a second data rate to apply to the second group of DSL linesbased on the data rates attainable as determined by the modeling, inwhich the second data rate for the second group is different than thefirst data rate for the first group; and instructing the DSL lines ofthe first and second groups to adopt the corresponding power parametersrequired to attain the selected first and second data ratesrespectively, in which different power parameters are specified for eachof the first and second groups of DSL lines.

In another alternative embodiment operations in a Digital SubscriberLine (DSL) communications system having a plurality of DSL lines,include: dividing the plurality of DSL lines into a first group of DSLlines and a second group of DSL lines based on characteristics of therespective plurality of DSL lines; assigning a first assumed loop lengthto all of the DSL lines of the first group; assigning a second assumedloop length to all of the DSL lines of the second group; estimating amaximum upstream data rate for each of the first and second groups ofDSL lines using the first and second assumed loop lengths respectively;identifying maximum upstream power parameters required to attain theestimated maximum upstream data rate for each of the first and secondgroups of DSL lines; and applying the maximum upstream power parametersidentified to the DSL lines of the first and second groups of DSL lines.

In another alternative embodiment operations in a Digital SubscriberLine (DSL) communications system having a plurality of DSL lines thereinincludes: dividing the plurality of DSL lines into two or more groups ofDSL lines based on characteristics of the respective plurality of DSLlines; in which processing for each of the two or more groups of DSLlines includes at least: (i) assigning an assumed loop length to all ofthe DSL lines within each respective group, (ii) estimating a maximumupstream data rate for each respective group of DSL lines, (iii)identifying maximum upstream power parameters required to attain theestimated maximum upstream data rate for each respective group of DSLlines, and (iv) applying the maximum upstream power parametersidentified to the DSL lines of the first and second groups of DSL lines.

In yet another alternative embodiment, operations include: dividing aplurality of DSL lines into a first group of DSL lines and a secondgroup of DSL lines based on characteristics common to each of the DSLlines within the respective first and second groups; modeling the firstand second groups of lines using a first assumed loop length for the DSLlines of the first group and using a second assumed loop length for theDSL lines of the second group; estimating a maximum upstream data ratefor each of the first and second groups of DSL lines based on themodeling; identifying maximum upstream power parameters required toattain the estimated maximum upstream data rate for each of the firstand second groups of DSL lines; and instructing the DSL lines of thefirst and second groups of DSL lines to adopt the maximum upstream powerparameters identified.

In accordance with a particular embodiment, the method 400 furtherincludes: prioritizing the first group of DSL lines over the secondgroup of DSL lines; and in which selecting upstream power controlparameters to apply to each of the first and second groups of DSL linesincludes selecting upstream power control parameters to enable anupstream data rate by the first group of DSL lines which is greater thanan upstream data rate by the second group of DSL lines.

In accordance with one embodiment of method 400, determining attainableupstream data rates for the first and second groups of DSL linesincludes modeling the first and second groups of DSL lines anddetermining the attainable upstream data rates based on the modeling.

In accordance with another embodiment of method 400, modeling includesestimating a maximum upstream data rate for each of the first and secondgroups of DSL lines and estimating corresponding power parameters toattain the maximum upstream data rates for the first and second groupsrespectively.

In accordance with another embodiment of method 400, the modelingfurther includes: assigning a first assumed loop length to all of theDSL lines of the first group; assigning a second assumed loop length toall of the DSL lines of the second group; and modeling the first andsecond groups of DSL lines to determine data rates attainable for eachof the first and second groups using the first and second assumed looplengths respectively, in which the modeling operates without regard toactual loop lengths of the plurality of DSL lines.

In accordance with another embodiment of method 400, the modelingfurther includes: identifying a maximum loop length among all the linesof the first group; identifying a maximum loop length among all thelines of the second group; and modeling the first and second groups oflines using the maximum loop length of the first group as an assumedloop length for all lines in the first group without regard to actualline lengths of the first group of lines and further using the maximumloop length of the second group as an assumed loop length for all linesin the second group without regard to actual line lengths of the secondgroup of lines.

In accordance with a particular embodiment, the method 400 furtherincludes: receiving as input for one or more models utilized by themodeling operations: an expected quantity of lines for the second group,an expected quantity of lines for the second group, or an expectedquantity of lines for each of the first and the second groups. In analternative embodiment, a ratio of lines may be utilized rather than aquantity, and thus, the inputs may include a ratio of an expectedquantity of lines for the first group or the second group based on anexpected quantity of lines provided for the second group or the firstgroup respectively.

In accordance with a particular embodiment, the method 400 furtherincludes: prioritizing the first group of lines to operate at anupstream data rate which is greater than the second group of lines by:(a) specifying an upstream data rate for the first group of lines over aminimum performance threshold; and (b) restricting an upstream data ratefor the second group of lines as necessary to enable the first group oflines to operate at the specified upstream data rate for the first groupof lines while the second group of lines operate simultaneously at therestricted upstream data rate. For example, operational performance ofthe second group of DSL lines may be sacrificed to some extent byrestricting the data rate of the second group in preference to theprioritized first group by exploiting the tradeoff performancerelationship between the two groups.

In accordance with another embodiment of method 400, the modelingfurther includes: determining a maximum upstream data rate for the linesof the prioritized first group by modeling the first and second groupsof lines based on the restricted upstream data rate for the secondgroup; and in which restricting the lines of the second group includesassigning restrictions based on the modeling which are configured topermit the prioritized first group to operate at the specified upstreamdata rate simultaneously with the second group of lines operating at therestricted upstream data rate according to the modeling.

In accordance with another embodiment of method 400, dividing aplurality of DSL lines into a first group of DSL lines and a secondgroup of DSL lines based on characteristics common to each of the DSLlines within the respective first and second groups includes one of thefollowing groupings: (i) the first group of lines having vectored linesand the second group of lines having non-vectored lines; (ii) the firstgroup of lines being coupled with vectoring capable CPE modems and thesecond group of lines being coupled with non-vectoring capable CPEmodems; (iii) the first group of lines being coupled with a firstequipment type and the second group of lines being coupled with a secondequipment type; (iv) the first group of lines having line lengths of athreshold range greater than the lines of the second group; (v) thefirst group of lines having line lengths less than a first maximumthreshold line length and the second group of lines having line lengthsgreater than or equal to a second maximum threshold line length; (vi)the first group of lines utilizing a frequency range transmission plandifferent than the lines of the second group; (vii) the first group oflines being associated with subscribers of a higher priced subscriptiontier than subscribers associated with the lines of the second group;(viii) the first group of lines being associated with subscribers ofcontractually promised a higher upstream data rate than subscribersassociated with the lines of the second group; and (ix) the first groupof lines being associated with subscribers of a DSL service productdifferent than subscribers associated with the lines of the secondgroup.

In accordance with another embodiment of method 400, selecting upstreampower control parameters includes: determining the upstream powercontrol parameters for the lines of the second group by identifyingupstream power back-off parameters that achieve a maximum upstream datarate for the lines of the second group; and determining the upstreampower control parameters for the lines of the first group by identifyingupstream power back-off parameters that achieve a maximum upstream datarate for the lines of the first group without negatively affecting themaximum upstream data rate for the lines of the second group when boththe first and second groups of lines simultaneously operate at theirrespective maximum upstream data rates.

In accordance with a particular embodiment, the method 400 furtherincludes: establishing an operational interface to a communicationssystem, the communications system having the plurality of DSL linestherein; in which the plurality DSL lines include a plurality of DSLtransmission lines, DSL loops, copper telephone lines, or twisted pairtelephone lines, the plurality of DSL lines carrying DSL communicationsignals; and further in which the plurality of DSL lines are compatiblewith at least one of the following DSL protocols: ADSL, VDSL, VDSL2,vectored VDSL2, and G.fast.

In accordance with another embodiment of method 400, selecting upstreampower control parameters includes: selecting a different upstream powerback off parameter for each of the first group of lines and the secondgroup of lines; selecting one or more additional parameters to apply toeach of the first and second groups of lines, the parameters selectedfrom the group including: a target bit rate, a range of target bitrates, a maximum bit rate, transmit power, a range of transmit powers, aPower Spectral Density (PSD) mask, a target noise margin, a maximumnoise margin, a carrier mask, and transmit passbands defining a set offrequencies over which data is transmitted; and further in which theadditional parameters selected are different for each of the first andsecond groups of lines.

In accordance with another embodiment of method 400, in which selectingupstream power control parameters comprises: identifying performancetradeoffs to each of the first and second groups such that improvedperformance to the first group is accompanied by degraded performance ofthe second group and visa-versa; and in which the method 400 furtherincludes prioritizing performance of the first group over the secondgroup to achieve an attainable upstream data rate for the first groupover a specified threshold or prioritizing performance of the firstgroup over the second group to maximize an attainable upstream data ratefor the first group.

In accordance with another embodiment of method 400, determiningattainable upstream data rates for the first and second groups of DSLlines includes estimating achievable performance targets for each of thefirst and second groups by performing the at least one of the followingoperations: (i) modeling a general estimation for an entire regionalloop plant encompassing the plurality of DSL lines based uponstatistical properties for the entire regional loop plant withoutrequiring per-line statistics for the plurality of DSL linesconstituting the first and second groups; (ii) modeling a specificknowledge estimation for the plurality of DSL lines based upon per-linestatistics for each the plurality of DSL lines including statistics forthe plurality of DSL lines selected from one or more of: a quantity oflines, cable and binder assignments for the lines, line lengths,crosstalk coupling levels amongst the lines, background noise levelsaffecting the lines, and exposure length defined as a part of the cablewhich is shared by the lines first group and the lines of the secondgroup through which crosstalk coupling occurs; and (iii) modeling aperformance based estimation based on operational performance of theplurality of DSL lines or operational capabilities for equipmentassociated with the plurality of DSL lines, or both.

In accordance with another embodiment of method 400, determiningattainable upstream data rates for the first and second groups of DSLlines includes estimating at least Far end crosstalk (FEXT) coupling foreach of the plurality of DSL lines according to estimated received FEXTpower for the respective line, where higher received FEXT power isindicative of stronger FEXT coupling into other lines among theplurality of DSL lines than lines associated with lower received FEXTpower.

In accordance with another embodiment of method 400, selecting upstreampower control parameters to apply to each of the first and second groupsof DSL lines based on the attainable upstream data rates determined,includes one or more of: weighting one or more of the selected upstreampower control parameters according to service levels for users in thefirst and second groups of lines; applying target bit rates and SNR(Signal-To-Noise) margin targets to the lines in the first group, thesecond group, or both the first and second groups; applying an upstreampower back-off (UPBO) to the lines in the first group, the second group,or both the first and second groups; applying a water filling criterionto determine bit-loadings and transmit Power Spectral Densities (PSDs)to the lines in the first group, the second group, or both the first andsecond groups; and coordinating assignment of the selected upstreampower control parameters with a centralized management system associatedwith a communications system within which the DSL lines operate to matchthe selected upstream power control parameters to be sent to the DSLlines via instructions.

In accordance with a particular embodiment, the method 400 furtherincludes: collecting operational data from the plurality of DSL lines;and further in which the determining attainable upstream data rates forthe first and second groups of DSL lines is based at least in part onthe operational data collected.

According to one embodiment, there is a non-transitory computer readablestorage medium or a computer program product having instructions storedthereon that, when executed by a processor in a management device, theinstructions cause the management device to perform operationsincluding: dividing a plurality of DSL lines into a first group of DSLlines and a second group of DSL lines based on characteristics common toeach of the DSL lines within the respective first and second groups;determining attainable upstream data rates for the first and secondgroups of DSL lines according to the characteristics of each group;selecting upstream power control parameters to apply to each of thefirst and second groups of DSL lines based on the attainable upstreamdata rates determined; and instructing the DSL lines of the first andsecond groups to adopt the selected upstream power control parameters.

In a particular embodiment, the instructions of the non-transitorycomputer readable storage medium or a computer program product enable amanagement device to perform any of the operations carried out by method300, method 400, and the related embodiments for such methods.

FIG. 5 illustrates a diagrammatic representation of a system 500 inaccordance with which embodiments may operate, be installed, integrated,or configured.

In one embodiment, system 500 includes a memory 595 and a processor orprocessors 596. For example, memory 595 may store instructions to beexecuted and processor(s) 596 may execute such instructions.Processor(s) 596 may also implement or execute implementing logic 560having logic to implement the methodologies discussed herein. System 500includes communication bus(es) 515 to transfer transactions,instructions, requests, and data within system 500 among a plurality ofperipheral devices communicably interfaced with one or morecommunication buses 515. System 500 further includes managementinterface 525, for example, to receive requests, return responses, andotherwise interface with network elements located separately from system500.

In some embodiments, management interface 525 communicates informationvia an out-of-band connection separate from DSL line basedcommunications, where “in-band” communications are communications thattraverse the same communication means as payload data (e.g., content)being exchanged between networked devices and where “out-of-band”communications are communications that traverse an isolatedcommunication means, separate from the mechanism for communicating thepayload data. An out-of-band connection may serve as a redundant orbackup interface over which to communicate control data between thesystem 500 and other networked devices or between the system 500 and athird party service provider.

System 500 further includes an interface to the DSL lines 530 tocommunicate information via a LAN based connection, to monitor the DSLlines, DSL loops, DSL twisted pairs, copper telephone lines, and Digitalcommunication lines which are interfaced to system 500. System 500further includes a database of line characteristics 550 that may beanalyzed or referenced when conducting analysis such as performanceestimation, modeling, and predictions as well as selection of upstreampower control parameters, power back off settings, and other functions.System 500 may further include multiple optimization instructions 555,any of which may be initiated responsive to analysis of the connectedDSL lines. For example, corrective actions, additional diagnostics,information probes, configuration change requests, local commands,remote execution commands, and the like may be specified by andtriggered as optimization instructions 555. The database of linecharacteristics 550 and the optimization instructions 555 may be storedupon a hard drive, persistent data store, a database, or other storagelocation within system 500.

Distinct within system 500 is management device 501 which includescollection module 570, performance estimation module 575, selectionmodule 580, line analysis module 585, and a configuration module 590.Management device 501 may be installed and configured in a compatiblesystem 500 as is depicted by FIG. 5, or provided separately so as tooperate in conjunction with appropriate implementing logic 560 or othersoftware.

In accordance with one embodiment there is a system having a processor596 and a memory 595 therein, in which the system 500 further includes:an interface 525 to a communications system, the communications systemhaving a plurality of DSL lines; a line analysis module 585 to dividethe plurality of DSL lines into a first group of DSL lines and a secondgroup of DSL lines based on characteristics common to each of the DSLlines within the respective first and second groups; a performanceestimation module 575 to determine attainable upstream data rates forthe first and second groups of DSL lines according to thecharacteristics of each group; a selection module 580 to select upstreampower control parameters to apply to each of the first and second groupsof DSL lines based on the attainable upstream data rates determined; anda configuration module 590 to instruct the DSL lines of the first andsecond groups to adopt the selected upstream power control parameters,for instance by communicating with the plurality of DSL lines of thefirst and second groups via the interface to the DSL lines 530.

In accordance with another embodiment, the system 500 may furtherinclude a collection module 570 to collect operational data from theplurality of DSL lines of the first and second groups. In such anembodiment, the performance estimation module 575 is to estimate amaximum upstream data rate for each the first and second groups of linesbased at least in part on the operational data collected via thecollection module 570 of the management device 501.

According to another embodiment, the system 500 operates as a server ofa cloud service provider physically remote from a Customer PremisesEquipment (CPE) modem at a business or residence of a DSL subscriberassociated with one of the plurality of DSL lines and physically remotefrom a Central Office (CO) which provides communication services to theCPE modem; and further in which the configuration module is to instructthe DSL lines of the first and second groups is to configure atransceiver of the CPE modem using the selected upstream power controlparameters.

FIG. 6 illustrates a diagrammatic representation of a machine 600 in theexemplary form of a computer system, in accordance with one embodiment,within which a set of instructions, for causing the machine 600 toperform any one or more of the methodologies discussed herein, may beexecuted. In alternative embodiments, the machine may be connected,networked, interfaced, etc., with other machines in a Local Area Network(LAN), a Wide Area Network, an intranet, an extranet, or the Internet.The machine may operate in the capacity of a server or a client machinein a client-server network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. Certain embodimentsof the machine may be in the form of a personal computer (PC), a tabletPC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellulartelephone, a web appliance, a server, a network router, switch orbridge, computing system, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while only a single machine is illustrated,the term “machine” shall also be taken to include any collection ofmachines (e.g., computers) that individually or jointly execute a set(or multiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The exemplary computer system 600 includes a processor 602, a mainmemory 604 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc., static memory such as flash memory, static random accessmemory (SRAM), volatile but high-data rate RAM, etc.), and a secondarymemory 618 (e.g., a persistent storage device including hard disk drivesand persistent data base implementations), which communicate with eachother via a bus 630. Main memory 604 includes information andinstructions and software program components necessary for performingand executing the functions with respect to the various embodiments ofthe systems, methods, and management device as described herein.Optimization instructions 623 stored within main memory 604 may betriggered based on, for example, analysis of collected operational data,known line statistics, known equipment capabilities and limitations, andso forth. Main memory further includes channel, crosstalk, and noisemodels 624 according to this embodiment which are stored within mainmemory 604 for use in estimating and predicting operationalcharacteristics of the lines undergoing evaluation. Main memory 604 andits sub-elements (e.g. 623 and 624) are operable in conjunction withprocessing logic 626 and/or software 622 and processor 602 to performthe methodologies discussed herein.

Processor 602 represents one or more general-purpose processing devicessuch as a microprocessor, central processing unit, or the like. Moreparticularly, the processor 602 may be a complex instruction setcomputing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,processor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processor 602 may alsobe one or more special-purpose processing devices such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), a digital signal processor (DSP), network processor, or thelike. Processor 602 is configured to execute the processing logic 626for performing the operations and functionality which is discussedherein.

The computer system 600 may further include one or more networkinterface cards 608 to communicatively interface the computer system 600with one or more networks 620 from which information may be collectedfor analysis. The computer system 600 also may include a user interface610 (such as a video display unit, a liquid crystal display (LCD), or acathode ray tube (CRT)), an alphanumeric input device 612 (e.g., akeyboard), a cursor control device 614 (e.g., a mouse), and a signalgeneration device 616 (e.g., an integrated speaker). The computer system600 may further include peripheral device 636 (e.g., wireless or wiredcommunication devices, memory devices, storage devices, audio processingdevices, video processing devices, etc.). The computer system 600 mayperform the functions of a management device 634 capable of interfacingwith digital communication lines such as copper telephone lines within avectored and non-vectored groups, monitoring, collecting, analyzing, andreporting information, and initiating, triggering, and executing variousoptimization instructions 623 including the execution of commands andinstructions to alter characteristics and operation of vectoringmechanisms and those lines associated with vectoring deployments.

The secondary memory 618 may include a non-transitory machine-readablestorage medium (or more specifically a non-transitory machine-accessiblestorage medium) 631 on which is stored one or more sets of instructions(e.g., software 622) embodying any one or more of the methodologies orfunctions described herein. Software 622 may also reside, oralternatively reside within main memory 604, and may further residecompletely or at least partially within the processor 602 duringexecution thereof by the computer system 600, the main memory 604 andthe processor 602 also constituting machine-readable storage media. Thesoftware 622 may further be transmitted or received over a network 620via the network interface card 608.

While the subject matter disclosed herein has been described by way ofexample and in terms of the specific embodiments, it is to be understoodthat the claimed embodiments are not limited to the explicitlyenumerated embodiments disclosed. To the contrary, the disclosure isintended to cover various modifications and similar arrangements as areapparent to those skilled in the art. Therefore, the scope of theappended claims should be accorded the broadest interpretation so as toencompass all such modifications and similar arrangements. It is to beunderstood that the above description is intended to be illustrative,and not restrictive. Many other embodiments will be apparent to those ofskill in the art upon reading and understanding the above description.The scope of the disclosed subject matter is therefore to be determinedin reference to the appended claims, along with the full scope ofequivalents to which such claims are entitled.

What is claimed is:
 1. A method comprising: dividing a plurality of DSLlines into a first group of DSL lines and a second group of DSL linesbased on characteristics common to each of the DSL lines within therespective first and second groups; determining attainable upstream datarates for the first and second groups of DSL lines according to thecharacteristics of each group; selecting a first set of upstream powerback-off (UPBO) parameters for the first group of DSL lines and a secondset of UPBO parameters for a second group of DSL lines based on theattainable upstream data rates determined; and instructing the DSL linesof the first and second groups to apply the selected first and secondset of UPBO parameters.
 2. The method of claim 1, further comprising:prioritizing the first group of DSL lines over the group of DSL lines,wherein selecting first and second set of UPBO parameters to for thefirst and second groups of DSL lines comprises selecting UPBO parametersaccording to a common objective for the first and second group of DSLlines.
 3. The method of claim 1, wherein determining attainable upstreamdata rates for the first and second groups of DSL lines comprisesmodeling the first and second groups of DSL lines and determining theattainable upstream data rates based on the modeling.
 4. The method ofclaim 3, wherein the modeling comprises estimating a maximum upstreamdata rate for each of the first and second groups of DSL lines andestimating corresponding power parameters to attain the maximum upstreamdata rates for the first and second groups respectively.
 5. The methodof claim 3, wherein the modeling further comprises: assigning a firstassumed loop length to all of the DSL lines of the first group;assigning a second assumed loop length to all of the DSL lines of thesecond group; and modeling the first and second groups of DSL lines todetermine data rates attainable for each of the first and second groupsusing the first and second assumed loop lengths respectively, whereinthe modeling operates without regard to actual loop lengths of theplurality of DSL lines.
 6. The method of claim 3, wherein the modelingfurther comprises: identifying a maximum loop length among all the linesof the first group; identifying a maximum loop length among all thelines of the second group; and modeling the first and second groups oflines using the maximum loop length of the first group as an assumedloop length for all lines in the first group without regard to actualline lengths of the first group of lines and further using the maximumloop length of the second group as an assumed loop length for all linesin the second group without regard to actual line lengths of the secondgroup of lines.
 7. The method of claim 3, further comprising: receivingas input for one or more models utilized by the modeling: an expectedquantity of lines for the second group, an expected quantity of linesfor the second group, or an expected quantity of lines for each of thefirst and the second groups.
 8. The method of claim 1, furthercomprising: prioritizing the first group of lines to operate at anupstream data rate which is greater than the second group of lines by:specifying an upstream data rate for the first group of lines over aminimum performance threshold; and restricting an upstream data rate forthe second group of lines as necessary to enable the first group oflines to operate at the specified upstream data rate for the first groupof lines while the second group of lines operate simultaneously at therestricted upstream data rate.
 9. The method of claim 8, furthercomprising: determining a maximum upstream data rate for the lines ofthe prioritized first group by modeling the first and second groups oflines based on the restricted upstream data rate for the second group;and wherein restricting the lines of the second group comprisesassigning restrictions based on the modeling which are configured topermit the prioritized first group to operate at the specified upstreamdata rate simultaneously with the second group of lines operating at therestricted upstream data rate according to the modeling.
 10. The methodof claim 1, further comprising at least one of: (i) the first group oflines having vectored lines and the second group of lines havingnon-vectored lines; (ii) the first group of lines being coupled withvectoring capable Customer Premises Equipment (CPE) modems and thesecond group of lines being coupled with non-vectoring capable CPEmodems; (iii) the first group of lines being coupled with a firstequipment type and the second group of lines being coupled with a secondequipment type; (iv) the first group of lines having line lengths of athreshold range less than the lines of the second group; (v) the firstgroup of lines having line lengths less than a first maximum thresholdline length and the second group of lines having line lengths greaterthan or equal to a second maximum threshold line length; (vi) the firstgroup of lines utilizing a frequency range transmission plan differentthan the lines of the second group; (vii) the first group of lines beingassociated with subscribers of a higher priced subscription tier thansubscribers associated with the lines of the second group; (viii) thefirst group of lines being associated with subscribers of contractuallypromised a higher upstream data rate than subscribers associated withthe lines of the second group; and (ix) the first group of lines beingassociated with subscribers of a DSL service product different thansubscribers associated with the lines of the second group.
 11. Themethod of claim 1, wherein selecting first and second set of UPBOparameters comprises: determining the UPBO parameters for the lines ofthe second group by identifying UPBO parameters that achieve a maximumupstream data rate for the lines of the second group; and determiningthe UPBO parameters for the lines of the first group by identifying UPBOparameters that achieve a maximum upstream data rate for the lines ofthe first group without negatively affecting the maximum upstream datarate for the lines of the second group when both the first and secondgroups of lines operate at their respective maximum upstream data rates.12. The method of claim 1, further comprising: establishing anoperational interface to a communications system that comprises theplurality of DSL lines, wherein the plurality DSL lines comprise aplurality of DSL transmission lines, DSL loops, copper telephone lines,or twisted pair telephone lines, the plurality of DSL lines carrying DSLcommunication signals and wherein the plurality of DSL lines arecompatible with at least one of the following DSL protocols: ADSL, VDSL,VDSL2, vectored VDSL2, and G.fast.
 13. The method of claim 1, furthercomprising: selecting a different UPBO parameter for each of the firstgroup of lines and the second group of lines; and selecting one or moreadditional parameters to apply to each of the first and second groups oflines, the additional parameters comprising at least one of: a targetbit rate, a range of target bit rates, a maximum bit rate, transmitpower, a range of transmit powers, a Power Spectral Density (PSD) mask,a target noise margin, a maximum noise margin, a carrier mask, ortransmit passbands defining a set of frequencies over which data istransmitted wherein the additional parameters selected are different foreach of the first and second groups of lines.
 14. The method of claim 1,further comprising: identifying performance tradeoffs to each of thefirst and second groups such that improved performance to the firstgroup is accompanied by degraded performance of the second group andvisa-versa, wherein the method further comprises prioritizingperformance of the first group over the second group to achieve anattainable upstream data rate for the first group over a specifiedthreshold or prioritizing performance of the first group over the secondgroup to maximize an attainable upstream data rate for the first group.15. The method of claim 1, wherein determining attainable upstream datarates comprises estimating achievable performance targets for each ofthe first and second groups by performing the at least one of thefollowing: i. modeling a general estimation for an entire regional loopplant encompassing the plurality of DSL lines based upon statisticalproperties for the entire regional loop plant without requiring per-linestatistics for the plurality of DSL lines constituting the first andsecond groups; ii. modeling a specific knowledge estimation for theplurality of DSL lines based upon per-line statistics for each theplurality of DSL lines including statistics for the plurality of DSLlines selected from one or more of: a quantity of lines, cable andbinder assignments for the lines, line lengths, crosstalk couplinglevels amongst the lines, background noise levels affecting the lines,and exposure length defined as a part of the cable which is shared bythe lines first group or the lines of the second group through whichcrosstalk coupling occurs; or iii. modeling a performance basedestimation based on operational performance of the plurality of DSLlines or operational capabilities for equipment associated with theplurality of DSL lines, or both.
 16. The method of claim 1, whereindetermining attainable upstream data rates comprises estimating at leastFar end crosstalk (FEXT) coupling for each of the plurality of DSL linesaccording to estimated received FEXT power for the respective line,where higher received FEXT power is indicative of stronger FEXT couplinginto other lines among the plurality of DSL lines than lines associatedwith lower received FEXT power.
 17. The method of claim 1, furthercomprising one or more of: weighting one or more of the selected UPBOparameters according to service levels for users in the first and secondgroups of lines; applying target bit rates and SNR (Signal-To-Noise)margin targets to the lines in the first group, the second group, orboth the first and second groups; applying UPBO parameters to the linesin the first group, the second group, or both the first and secondgroups; applying a waterfilling criterion to determine bit-loadings andtransmit Power Spectral Densities (PSDs) to the lines in the firstgroup, the second group, or both the first and second groups; orcoordinating assignment of the selected UPBO parameters with acentralized management system associated with a communications systemwithin which the DSL lines operate to match the selected UPBO parametersto be sent to the DSL lines via instructions.
 18. The method of claim 1,further comprising collecting operational data from the plurality of DSLlines, wherein the determining attainable upstream data rates is basedat least in part on the operational data collected.
 19. A non-transitorycomputer readable storage medium having instructions stored thereonthat, when executed by a processor in a management device, theinstructions cause the management device to perform operationscomprising: dividing a plurality of DSL lines into a first group of DSLlines and a second group of DSL lines based on characteristics common toeach of the DSL lines within the respective first and second groups;determining attainable upstream data rates for the first and secondgroups of DSL lines according to the characteristics of each group;selecting a first set of upstream power back-off (UPBO) parameters forthe first group of DSL lines and a second set of UPBO parameters for asecond group of DSL lines based on the attainable upstream data ratesdetermined; and instructing the DSL lines of the first and second groupsto apply the selected first and second set of UPBO parameters.
 20. Asystem comprising: an interface to a communications system, thecommunications system having a plurality of DSL lines; a line analysismodule to divide the plurality of DSL lines into a first group of DSLlines and a second group of DSL lines based on characteristics common toeach of the DSL lines within the respective first and second groups; aperformance estimation module to determine attainable upstream datarates for the first and second groups of DSL lines according to thecharacteristics of each group; a selection module to select a first setof UPBO parameters for the first group of DSL lines and a second set ofUPBO parameters for a second group of DSL lines based on the attainableupstream data rates determined; and a configuration module to instructthe DSL lines of the first and second groups to apply the selected UPBOparameters.
 21. The system of claim 20, further comprising a collectionmodule to collect operational data from the plurality of DSL lines ofthe first and second groups, wherein the performance estimation moduleis to estimate a maximum upstream data rate for each the first andsecond groups of lines based at least in part on the operational datacollected.
 22. The system of claim 20, wherein the system operates as aserver of a cloud service provider physically remote from a CustomerPremises Equipment (CPE) modem of a DSL subscriber associated with oneof the plurality of DSL lines and physically remote from a CentralOffice (CO) which provides communication services to the CPE modem,wherein the configuration module to instruct the DSL lines of the firstand second groups is to configure a transceiver of the CPE modem usingthe selected UPBO parameters.